|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC - Proposed Standard approved July 2005
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses UUIDs as defined in the reference
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4122
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard". Errata exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Zahn, L., Dineen, T., and P. Leach, "Network Computing/
Architecture", ISBN 0-13-611674-4, January 1990./
/
[2] "DCE: Remote Procedure Call", Open Group CAE Specification C309,/
ISBN 1-85912-041-5, August 1994./
/
[3] ISO/IEC 9834-8:2004 Information Technology, "Procedures for the/
operation of OSI Registration Authorities: Generation and/
registration of Universally Unique Identifiers (UUIDs) and their/
use as ASN.1 Object Identifier components" ITU-T Rec. X.667,/
2004./
/
[4] Rivest, R., "The MD5 Message-Digest Algorithm ", RFC 1321, April/
1992./
[5] Eastlake, D., 3rd, Schiller, J., and S. Crocker, "Randomness/
Requirements for Security", BCP 106, RFC 4086, June 2005./
/
[6] Moats, R., "URN Syntax", RFC 2141, May 1997./
/
[7] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", RFC 2234, November 1997./
/
[8] National Institute of Standards and Technology, "Secure Hash/
Standard", FIPS PUB 180-1, April 1995,/
http://www.itl.nist.gov/fipspubs/fip180-1.htm./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
